Composer Packages with Version Constraints


Control which versions of Composer packages should be installed in your project using version constraints.

{
    "require": {
        "livewire/livewire": "^2.0"
    }
}

When specifying "livewire/livewire": "^2.0" like this in the composer.json file, it ensures Composer installs version 2.0 or higher.

Constraints that can be used :

1. ^ (Caret Constraint):

Most recent minor version of the specified release series. Here specified series is 2.x means 2.1, 2.2 upto 2.9.

"require": {
        "livewire/livewire": "^2.0"
    }

2. ~ (Tilde Constraint):

Most recent patch version of the specified release series.

~2.0 version includes versions 2.0, 2.1, 2.2 ... , but not including, 3.0

~1.2 allows versions 1.2, 1.2.1, 1.2.2 ..., but not including, 1.3

"require": {
        "livewire/livewire": "~2.0"
    }

3. >= (Greater Than or Equal To)

Minimum acceptable version. >=1.0 allows any version 1.0 or higher.

"require": {
        "livewire/livewire": ">=1.0"
    }

4. <= (Less Than or Equal To) :

Maximum acceptable version. <=2.0 allows any version less than 2, including 2.0.

"require": {
        "livewire/livewire": "<=2.0"
    }

You Might Also Like

Use Query Scopes for Reusable Queries

Encapsulate common query logic within model scopes to keep your code DRY (Don't Repeat Yourself). Sc...

Custom Blade Directives in Laravel

# Step 1: Create a Custom Blade Directive Add custom directives in the boot method of a service prov...